Skip to content

[Snyk] Upgrade react-error-boundary from 4.0.13 to 4.1.2#139

Merged
jlbooker merged 2 commits intomainfrom
snyk-upgrade-7942014e051ab6c895740f4045e2841e
Sep 13, 2025
Merged

[Snyk] Upgrade react-error-boundary from 4.0.13 to 4.1.2#139
jlbooker merged 2 commits intomainfrom
snyk-upgrade-7942014e051ab6c895740f4045e2841e

Conversation

@jlbooker
Copy link
Member

snyk-top-banner

Snyk has created this PR to upgrade react-error-boundary from 4.0.13 to 4.1.2.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 3 versions ahead of your current version.

  • The recommended version was released a year ago.

Release notes
Package name: react-error-boundary
  • 4.1.2 - 2024-10-19
    • Remove engines field from Package JSON entirely
  • 4.1.1 - 2024-10-17
    • Remove node constraint from engines
  • 4.1.0 - 2024-10-15
    • Relax fallback prop to support broader ReactNode type
  • 4.0.13 - 2024-03-01

    Removed references to ESLint config kcd-scripts from package.json

from react-error-boundary GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

snyk-bot and others added 2 commits September 10, 2025 06:47
Snyk has created this PR to upgrade react-error-boundary from 4.0.13 to 4.1.2.

See this package in npm:
react-error-boundary

See this project in Snyk:
https://app.snyk.io/org/jlbooker/project/7cf1855e-e9b1-4adc-be76-4d02639c5e1d?utm_source=github&utm_medium=referral&page=upgrade-pr
@jlbooker jlbooker merged commit 9a73cf1 into main Sep 13, 2025
3 checks passed
@jlbooker jlbooker deleted the snyk-upgrade-7942014e051ab6c895740f4045e2841e branch September 13, 2025 13:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants